-
Notifications
You must be signed in to change notification settings - Fork 14.9k
[AVR] Fix for issue #163015, occasional corruption in stack passed params #164001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Closes #163015 |
…register pressure. See this forum discussion for details (or the GitHub issue) https://discourse.llvm.org/t/avr-register-allocation-issue-help-advice-with-debugging/88498/11 @aykevl @benshi001
64b7aad
to
aa54b9a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please use update_llc_test_checks.py to generate CHECK lines. Also, is there any reason you need -v -dump-input always
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is not needed to run update_llc_test_checks.py
, since the key check point in this test are the CHECK-NOT
lines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is up to reviewer to mark resolved/unresolved.
@mshockwave Do you have any more concerns for that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As my inline comments.
previous PR that I accidentally closed: #163082 |
Corruption can occur with passing parameters on the stack when under register pressure.
See this forum discussion for details (or the GitHub issue) https://discourse.llvm.org/t/avr-register-allocation-issue-help-advice-with-debugging/88498/11
@aykevl @benshi001